home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 4. _C_h_a_n_g_e_s__a_n_d__A_d_d_i_t_i_o_n_s
-
- _L_o_c_a_l_i_z_a_t_i_o_n_s _u_p_d_a_t_e_d
-
- SGImeeting 2.0.3a updated the localized documentation
- and on-line help. No changes to functionality were
- introduced.
-
-
- _I_c_o_n_s _a_n_d _p_i_x_m_a_p_s _u_p_d_a_t_e_d
-
- In SGImeeting 2.0.3 many icons and pixmaps have been
- updated to make the application more consistent with
- the IRIX desktop. These changes do not affect
- functionality.
-
-
- _I_n_t_e_r_o_p_e_r_a_b_i_l_i_t_y _p_r_o_b_l_e_m_s _i_n _J_a_p_a_n_e_s_e _l_o_c_a_l_e_s
-
- When running in a Japanese locale SGImeeting 2.0.1 and
- earlier would fail to transfer text (such as in the
- chat dialog) in the encoding NetMeeting expected. This
- is fixed in SGImeeting 2.0.2.
-
-
- _T_r_u_e _C_o_l_o_r _N_e_t_M_e_e_t_i_n_g _s_c_r_e_e_n _d_u_m_p_s _a_r_e _n_o_t _s_u_p_p_o_r_t_e_d
-
- Screen images created with the "PrintScreen" key on a
- PC running in True Color mode will not display in
- SGImeeting when pasted into a shared whiteboard. In
- SGImeeting 2.0.1 and earlier such images were silently
- discarded; starting with SGImeeting 2.0.2 an
- appropriately sized grey rectangle is displayed in
- their place. Images obtained with the NetMeeting area
- selection or window selection tools display correctly.
-
-
- _P_r_o_c_e_s_s _n_a_m_e_s _a_r_e _m_o_r_e _u_n_i_f_o_r_m
-
- Processes created by SGImeeting 2.0.2 are now easier to
- recognize, as they begin with "sgim_".
-
-
- _M_a_c_h_i_n_e-_s_p_e_c_i_f_i_c _m_i_s_b_e_h_a_v_i_o_r_s
-
- SGImeeting 2.0 and earlier would sometimes fail in
- unpredictable ways on specific systems due to memory
- layout conflicts. This is fixed in SGImeeting 2.0.1.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- _C_r_a_s_h _i_n _T._1_2_6 _W_B _m_o_v_i_n_g _l_a_r_g_e _i_m_a_g_e _a_s _i_t _j_o_i_n_s _a _c_a_l_l.
-
- SGImeeting 2.0 and earlier whiteboard would sometimes
- crash when attempting to join conferences that had
- large images in their whiteboards. This bug is fixed
- in SGImeeting 2.0.1.
-
-
- _I_P_v_6 _a_d_d_r_e_s_s _b_u_f_f_e_r _o_v_e_r_r_u_n_s
-
- Long (IPv6) addresses caused buffer overrun problems in
- SGImeeting 2.0 and earlier. This bug is fixed in
- SGImeeting 2.0.1.
-
-
- _E_n_h_a_n_c_e_d _N_e_t_M_e_e_t_i_n_g _3._0 _i_n_t_e_r_o_p_e_r_a_b_i_l_i_t_y
-
- NetMeeting 3.0 interoperability has been improved.
- SGImeeting 2.0 can operate in two modes: SGImeeting 1.x
- compatibility mode preserves the behavior of previous
- releases; NetMeeting 3.0 compatibility mode lets
- SGImeeting control applications shared by NetMeeting
- 3.0, and causes shared applications to appear in their
- own shadow window rather than on the desktop as in
- previous releases. The compatibility mode can be set
- in the Tools > Options menu.
-
-
- _S_p_e_e_d_d_i_a_l_s
-
- Speeddial (.cnf) files can be created via the Call >
- Create Speeddial menu, and invoked through the Address
- Book or the "-speeddial" command line option.
-
-
- _R_u_n-_i_n-_B_a_c_k_g_r_o_u_n_d
-
- The new Call > Run in Background menu entry will let
- you exit the SGImeeting user interface, but leave the
- application running. When an incoming call is received
- the user interface will be reloaded and you will be
- prompted to accept or reject the call as normal.
-
-
- _G_r_o_u_p_e_d _w_i_n_d_o_w _s_h_a_r_i_n_g
-
- Applications with a common X Class Name can be shared
- as a group by adding a
- "PropertyIndex.<window_class>_AUTOSHARE:" line to
- /usr/SGImeeting/config/sgimeeting.
-
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-